Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The Linux NFS Server must not have the insecure file locking option.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-4339 | GEN000000-LNX00560 | SV-37316r1_rule | IAIA-1 IAIA-2 | High |
| Description |
|---|
| Insecure file locking could allow for sensitive data to be viewed or edited by an unauthorized user. |
| STIG | Date |
|---|---|
| Red Hat Enterprise Linux 5 Security Technical Implementation Guide | 2013-07-03 |
Details
| Check Text ( C-36008r1_chk ) |
|---|
| Determine if an NFS server is running on the system by: # ps -ef |grep nfsd If an NFS server is running, confirm it is not configured with the insecure_locks option by: # exportfs -v The example below would be a finding: /misc/export speedy.example.com(rw,insecure_locks) |
| Fix Text (F-4250r3_fix) |
|---|
| Remove the "insecure_locks" option from all NFS exports on the system. Procedure: Edit /etc/exports and remove all instances of the insecure_locks option. Re-export the file systems to make the setting take effect. # exportfs -a |